Tested on JetKVM hardware after deploy. Digitizer emulation is perfect, coordinates are well aligned and smooth, and the aspect ratio is correct. Removes the stray Android Back/Home/Recents overlay from the known-good 657c72b baseline.

Tested on JetKVM hardware after deploy. Desktop usability is unchanged, phone usability remains good, and the Android controller view hides the desktop chrome and button strip automatically without manual URL arguments.

Add the Android controller APK source and backend handoff so Android WebView clients use the native login activity instead of the vanilla web login page. The APK now asks only for JetKVM IP/host plus password, preserves Autofill support, submits to /auth/login-local, stores returned cookies, and uses the JetKVM primary blue for the login button.

The backend serves a no-store native-login bridge for Android controller clients on /login-local and for unauthenticated Android HTML navigation through the SPA catch-all, while normal desktop browsers still receive the vanilla SPA.

Tested: go test ./... with local Go caches; release APK build; installed controller APK 1.10 on the Pixel 7a; deployed and verified the JetKVM backend hash; confirmed Android root requests receive the native handoff, normal browser root requests receive the SPA, Bitwarden Autofill appears, and manual logout returns to the native login activity.

Known limitation: after selecting a password from the Autofill service, the on-screen keyboard may remain open. This is app-side polish and will be addressed in the next commit by explicitly collapsing the IME after Autofill/login input.

Fixes the known limitation documented in ec4ded3: after selecting a password from the Autofill service, the on-screen keyboard could remain open over the native login screen.

Use a small AutofillAwareEditText wrapper for the password field so the APK responds to Android's actual autofill callback rather than guessing from text timing. When Autofill populates the password, the app waits briefly, clears password focus, and hides the IME.

Tested: release APK build, installed on the Pixel 7a, and verified the Autofill password selection now collapses the OSK while preserving the prior native login flow.

Restore and update the JetKVM companion APK source on this branch.

Remove the arm companion and trusted keyguard dismiss test buttons from the settings UI, simplify permission button labels, and show direct granted/not granted permission status text.

Align the companion settings background and button blue with the native Android login activity, and bump the companion package to versionCode 6 / versionName 1.5.

Built the release APK and installed it on the Pixel 8 for visual verification; backend Go tests also passed.

Prefer the relative mouse HID path for wheel reports when it is available, keeping absolute mouse wheel as a fallback.

Track the current relative mouse button state and include it in wheel reports so scrolling does not synthesize a button release.

Add focused tests for relative mouse and wheel report byte layout.

Validated on the Pixel 8 target: direct relative HID wheel reports scroll Android Settings, the deployed experiment backend scrolls through the viewer, and digitizer/aspect behavior remained unchanged.

Remove the inert fullscreen entry from the Android compact hamburger menu.

Expose a controller-side IME bridge that opens Android's OSK and forwards committed text through the existing JetKVM keyboard macro path, preserving desktop virtual keyboard fallback behavior.

Replace the fork README with a fresh upstream README copy plus a clearly separated Android support overview.

Describe the validated touchscreen/aspect baseline, controller APK, compact overlay, native login, Android OSK bridge, display toggle, wheel scrolling, and target companion APK so the fork purpose and implementation are clear before the vanilla upstream documentation.

The upstream wake HID function and the Android touchscreen digitizer both need hid.usb3 on this hardware. The device kernel does not expose hid.usb4, so keep wake_hid enabled only when touchscreen is disabled and route wake behavior through a harmless no-touch touchscreen report when touchscreen owns the slot.

Also preserve enabled config symlinks when a disabled gadget item shares the same config path, which prevents disabled wake_hid from removing the active touchscreen hid.usb3 link during config writes.

Validated with go test ./internal/usbgadget, make build_dev, and a live JetKVM sanity check showing the debug binary hash matched, USB was configured, and hid.usb3 used the touchscreen report length.